Method and Device for Data Capture for Push Over Cellular

ABSTRACT

A system ( 100 ) and method ( 300 ) for data record and playback for push-over-cellular (PoC) is provided. The method can include receiving ( 302 ) a push-to-talk (PTT) key-up from a first mobile device during a group dispatch call, identifying ( 304 ) the first mobile device from the PTT key-up to produce a first contact identifier ( 361 ), recording ( 306 ) data during the PTT key-up until a PTT key-down is received to produce a PTT recorded segment ( 311 ), marking ( 308 ) the PTT recorded segment with the contact identifier, and storing ( 310 ) the first PTT recorded segment to memory. The method steps can be repeated for creating a marked PTT conversation ( 360 ). The marked PTT conversation can be played back ( 230 ) by contact identifier, or played back ( 240 ) by call session. During playback, a contact identifier for each PTT recorded segment can be visually or audibly presented.

FIELD OF THE INVENTION

The present invention relates to wireless communication systems, andmore particularly, to data recording and playback.

BACKGROUND OF THE INVENTION

The use of portable electronic devices and mobile communication deviceshas increased dramatically in recent years. Two primary means of voicecommunication are generally offered in mobile devices: Interconnect anddispatch. Interconnect is a communication mode by which both parties canspeak at the same time. It is considered a two-way communication sinceboth parties can talk and listen on a separate talk channel and aseparate receive channel. Interconnect communication is also availablefor three-way calling or group call. In contrast, dispatch mode is acommunication mode by which only one party can speak at a time. Theother party can only listen until the first party finishes talking. Inpractice, a push-to-talk (PTT) key is pressed to acquire control of atalk channel. The talk channel is not released until the PTT key isreleased. Upon release, another participant can acquire the PTT channel.Dispatch mode is also available for three-way dispatch or groupdispatch.

Push-over-cellular (PoC) is one mode of operation whereby dispatchcommunication is enabled over a cellular infrastructure. SelectedDynamic Group Call (SDGC) is a form of dispatch call using PoC. SDGCprovides a way for all participating mobile devices to talk to eachother as on a group call, but it is characterized by creating the groupdynamically. SDGC provides fast call setup and operation that incomparison to traditional 3-way interconnect or conference calling.Similarly, SDGC only allows one participant to talk at a time.

Voice Record (VR) is a mobile device feature that can be used to recordan entire SDGBC call. In current practice, the entire call is recordedand stored as a call session. A user can replay the entire call sessionto hear portions the caller may have missed during the PoC call.However, because the entire call is stored, the user must generallylisten to the entire call. The call session is also generally stored bydate. Accordingly, the user must also generally know when the call wasrecorded in order to retrieve the call session. Furthermore, during aPoC group call, such as SDBC, many participants may talk during thecall, and the call may last for a long time. Accordingly, the user mayhave to wait to hear portions of the stored call session during replay.This may cause further frustration if the listener is required to listento the entire call to hear only one portion of the call.

SUMMARY

Broadly stated embodiments of the invention are directed to a device andmethod for marking data recordings during a group dispatch call inpush-over-cellular (PoC), and playing back the data recordings based onthe markings. The method for PoC can include recording a push-to-talkPTT conversation in PTT recorded segments, identifying mobile devicesfrom PTT key-ups during the PTT conversation, assigning contactidentifiers to the PTT recorded segments to produce a marked PTTconversation based on the identifying, and saving the marked PTTconversation to memory. A PTT recorded segment can be a data recording,such as voice or video, between a time of a PTT key-up and a PTTkey-release. A contact identifier can identify a mobile device, or auser of the mobile device, performing the PTT key-up. A contactidentifier can also include a name of a call session, a time of the PTTrecorded segment, or a length of the PTT recorded segment. The contactidentifier can be retrieved from push-to-transmit (PTX) data associatedwith the PTT key-up.

In one configuration, the marked PTT conversation can be sorted bycontact identifier, and played back in order of recording. Only the PTTrecorded segments that match the contact identifier are played back.This allows a user to play back PTT recorded segments of a particulartalker, based on the contact identifier. In another configuration, themarked PTT conversation can be played back in entirety with contactidentifiers. The contact identifiers can be visually or audiblypresented for each PTT recorded segment during a playback of the markedPTT conversation. For example, a name of a user that corresponds to aPTT recorded segment can be visually displayed. As another example, thename of the user can be pre-appended to the PTT recorded segment toaudibly identify the person talking.

One embodiment is a method for call session recording and playback in apush-over-cellular (PoC) system. The method can include receiving apush-to-talk (PTT) key-up from a first mobile device during a groupdispatch call, identifying the first mobile device from the PTT key-upto produce a first contact identifier, recording data during the PTTkey-up until a PTT key-down is received, marking the data with the firstcontact identifier to produce a first PTT recorded segment, and storingthe first PTT recorded segment to memory. The method steps of receiving,identifying, recording, marking, and storing can be repeated for aplurality of mobile devices on the group dispatch call. The step ofrepeating can produce a marked PTT conversation having multiple PTTrecorded segments each separately marked by a contact identifier.

Playback of the marked PTT conversation can be performed by contactidentifier or call session. In playback by contact identifier, themethod can include receiving a request to retrieve PTT recorded segmentsassociated with a contact identifier, and presenting the PTT recordedsegments for the contact identifier in order of recording in response tothe request. In playback by call session, the method can includeidentifying a call session associated with the marked PTT conversation,and playing back the PTT recorded segments by the call session in orderof recording. During playback, a contact identifier corresponding to aPTT recorded segment can be visually or audibly presented. For example,a voice tag can be pre-appended on a PTT recorded segment to audiblyidentify the contact. As another example, a name of the talker can bepresented on a display of a mobile device to identify the persontalking.

One embodiment is directed to a mobile device for call session recordingand playback suitable for use in push-over-cellular (PoC). The mobiledevice can include a push-to-talk (PTT) key for acquiring a talk channeland communicating data during a PTT group call, a recorder that recordsthe PTT group call in PTT recorded segments, and a processor thatassigns contact identifiers to the PTT recorded segments to produce amarked PTT conversation. A PTT recorded segment can be a recording ofdata between a time of a PTT key-up and a PTT key-release. The data canbe voice, video, or audio. A contact identifier can identify a mobiledevice performing the PTT key-up and a PTT key-release. A contactidentifier can be retrieved from push-to-transmit (PTX) data such as aniCard or event message provided through PoC systems. The processor canidentify other mobile devices that acquire the talk channel, andgenerate a contact identifier for the other mobile devices. The contactidentifier can include a name of a user of the mobile device, a time thetalk channel is acquired, and a length of the PTT recorded segment. Theprocessor can playback the marked PTT conversation by contact identifieror by call session. In playback by call identifier, the processor cansort the marked PTT conversation by contact identifier, and play backthe PTT recorded segments by contact in order of recording, in responseto a request. In playback by call session, the processor can visually oraudibly present a contact identifier of each PTT recorded segment. Themobile device can include a text-to-speech engine for synthesizing avoice tag from a contact identifier and pre-appending the voice tag to aPTT recorded segment. This allows the user to audibly identify thetalker of the PTT recorded segment in marked PTT conversation.

BRIEF DESCRIPTION OF THE DRAWINGS

The features of the system, which are believed to be novel, are setforth with particularity in the appended claims. The embodiments herein,can be understood by reference to the following description, taken inconjunction with the accompanying drawings, in the several figures ofwhich like reference numerals identify like elements, and in which:

FIG. 1 is a block diagram of a wireless communication system inaccordance with the embodiments of the invention;

FIG. 2 is a block diagram of a mobile device for data capture inaccordance with the embodiments of the invention;

FIG. 3 is an in-call screen for visually identifying a talker inaccordance with the embodiments of the invention;

FIG. 4 is a method for data capture in accordance with the embodimentsof the invention;

FIG. 5 is an exemplary push-to-talk (PTT) conversation in accordancewith the embodiments of the invention;

FIG. 6 is a depiction of the PTT conversation of FIG. 5 in accordancewith the embodiments of the invention;

FIG. 7 is a marked PTT conversation in accordance with the embodimentsof the invention;

FIG. 8 is a method for playback based on contact identifier inaccordance with the embodiments of the invention;

FIG. 9 is a depiction of PTT recorded segments for a contact identifierin accordance with the embodiments of the invention;

FIG. 10 is a playback of data based on contact identifier in accordancewith the embodiments of the invention;

FIG. 11 is a method for playback based on call session in accordancewith the embodiments of the invention;

FIG. 12 is a depiction of a marked PTT conversation based on callsession in accordance with the embodiments of the invention; and

FIG. 13 is a playback of data based on call session in accordance withthe embodiments of the invention.

DETAILED DESCRIPTION

While the specification concludes with claims defining the features ofthe embodiments of the invention that are regarded as novel, it isbelieved that the method, system, and other embodiments will be betterunderstood from a consideration of the following description inconjunction with the drawing figures, in which like reference numeralsare carried forward.

As required, detailed embodiments of the present method and system aredisclosed herein. However, it is to be understood that the disclosedembodiments are merely exemplary, which can be embodied in variousforms. Therefore, specific structural and functional details disclosedherein are not to be interpreted as limiting, but merely as a basis forthe claims and as a representative basis for teaching one skilled in theart to variously employ the embodiments of the present invention invirtually any appropriately detailed structure. Further, the terms andphrases used herein are not intended to be limiting but rather toprovide an understandable description of the embodiment herein.

The terms “a” or “an,” as used herein, are defined as one or more thanone. The term “plurality,” as used herein, is defined as two or morethan two. The term “another,” as used herein, is defined as at least asecond or more. The terms “including” and/or “having,” as used herein,are defined as comprising (i.e., open language). The term “coupled,” asused herein, is defined as connected, although not necessarily directly,and not necessarily mechanically.

The term “talk channel” can be defined as a transmit communicationchannel that is shared amongst a plurality of mobile devices. The term“hang-time” can be defined as the time between when a talk channel isreleased until the talk channel is again acquired. The term “PTTrequest” can be defined as an attempt to push to talk, either byhardware or software. The term “PTT key” can be defined as a physicalbutton or a soft-key. The term “PTT key-up” can be defined as acquiringthe transmit channel in response to a PTT request. The term “PTTkey-release” can be defined as the releasing of the transmit channel inresponse to releasing the PTT key. The term “soft-key” can be defined asa software controlled button. The term “PTT group call” can be definedas a group call based on push-to-talk requests. The term “contactidentifier” can be defined as a tag, or marking, associated with a PTTrecorded segment that identifies a source of the data captured withinthe PTT recorded segment. The source can be a mobile device identifier,or a name of a user that is using the mobile device. The term “PTTrecorded segment” can be defined as data that is captured on a talkchannel between a PTT key-up and a PTT key-release. The term “playbackby contact identifier” can be defined as replaying a recorded callsession that only includes PTT recorded segments associated with thecontact identifier. The term “playback by call session” can be definedas replaying a recorded call session with contact identifier informationfor at least one PTT recorded segment. The contact identifiers can bepresented with their associated PTT recorded segments in a visual oraudio format. The term “group dispatch call” can be defined as acontinuous communication between a plurality of mobile device. The term“PTT conversation” can be defined as voice segments or data segmentswithin a group dispatch call that are demarcated by a PTT key-up and aPTT key-release.

Referring to FIG. 1, a wireless communication system 100 for providinginterconnect and dispatch communication is shown. The wireless system100 can provide wireless connectivity or dispatch push-over-cellular(PoC) connectivity over a radio frequency (RF) communication network.The wireless communication system 100 can include a plurality of mobiledevices 110-112 for providing voice communication. In one arrangement,the mobile devices 110-112 can communicate with one or more cellulartowers 105 using a standard communication protocol such as CDMA, GSM, oriDEN, but is not herein limited to these. The cellular towers 105, inturn, can connect the mobile devices 110-112 through a cellularinfrastructure to other mobile devices or resources on other networks(not shown). The cellular towers 105 can also connect to one or moreservers for storing data, such as group dispatch calls, or morespecifically, PTT conversations. As an example, the mobile device 110can record a PTT conversation and save the PTT conversation locally tothe mobile device 110, or to a server on the wireless communicationsystem 100.

The mobile devices 110-112 can also connect amongst one another over aWide Local Area Network (WLAN) 104 within an ad-hoc group. A WLANprovides wireless access within a local geographical area. The mobiledevices 110-112 can communicate with the WLAN 104 according to theappropriate wireless communication standard. The WLAN 104 can coordinatea sending and receiving of voice packets between the mobile devices110-112. In another arrangement, the mobile devices 110-112 cancommunicate amongst themselves in a peer-to-peer ad-hoc network withoutinfrastructure or WLAN support. For example, the mobile devices can useshort-range radio communication to engage in a group call in apeer-to-peer mode. In a typical WLAN implementation, the physical layercan use a variety of technologies such as 802.11b or 802.11g WirelessLocal Area Network (WLAN) technologies. The physical layer may useinfrared, frequency hopping spread spectrum in the 2.4 GHz Band, ordirect sequence spread spectrum in the 2.4 GHz Band, or any othersuitable communication technology.

Mobile devices 110-112 can communicate together in a group dispatch callover the push-to-cellular (PoC) wireless communication system 100. Inthe group dispatch call, there is only one talk channel. In dispatchmode, only one mobile device at a time can acquire the talk channel.When the talk channel is acquired, the mobile device can transmit data,such as voice or video, to the other mobile devices listening on thechannel; that is, those devices engaged in the group dispatch call. Itshould be noted, that each mobile device can record the data sent on thetalk channel from the other mobile devices during the PTT conversation.A mobile device can also record data sent by the mobile device itself.

Briefly, a mobile device, such as mobile device 110, can record the PTTconversation in PTT recorded segments (see 210). Each PTT recordedsegment can be associated with a mobile device, or a user of the mobiledevice. The mobile device 110 can identify which of the other mobilesdevices in the group dispatch call provide the data on the talk channel.In one arrangement, the mobile device 110 can identify mobile devices inresponse to a push-to-talk (PTT) request. The PTT request can includeidentifying information, such as a mobile identification, or a name of auser. In particular, participants engaging in a group dispatch call in aPoC system generally send identifying information with a PTT request.For example, in a PoC group call, every participant sends differentpush-to-transmit (PTX) data by PTT push. The mobile device 110 canreview the PTX data to identify voice data associated with mobile device111, and identify voice data associated with mobile device 112. Themobile device 110 can assign contact identifiers to the voice data basedon the identification. In particular, the mobile device 110 can mark thePTT conversation with the contact identifiers (see 220). In practice,the mobile device 110 can determine which mobile devices are active onthe talk channel. Upon marking the PTT conversation, the mobile devicecan retrieve data associated with a specific mobile device by thecontact identifier. In one arrangement, the mobile device can playbackdata by contact identifier (see 230). In another arrangement, the mobiledevice can playback the PTT conversation by call session (see 240).

Referring to FIG. 2, a block diagram of a mobile device 110 is shown.The mobile device 110 can be a cell-phone, a personal digital assistant,a portable music player, an electronic map, a navigation system or anyother suitable communication device. The mobile device 110 can include amodem 120 for providing transmit and receive communication during agroup dispatch call, a push-to-talk (PTT) key 122 for acquiring aone-way dispatch voice communication over a transmit channel, a recorder124 operatively coupled to the transmit channel for recording the groupdispatch call in PTT recorded segments, a processor 126, or data-captureand information processing module, operatively coupled to the recorder124 and the modem 120 for assigning contact identifiers to the PTTrecorded segments, a display 128 for visually presenting contactidentifiers associated with the PTT recorded segments, and atext-to-speech (TTS) engine 129 for converting contact identifiers toaudio. The mobile device 110 can include a microphone 121 for capturingvoice, or audio, and the speaker 125 for playing voice, or audio, as isknown in the art.

Referring to FIG. 3, an in-call screen 140 is displayed. The in-callscreen 140 can be presented on the display 140 during a playback of amarked PTT conversation. Briefly, the in-call screen 140 identifies asource of a PTT recorded segment of the PTT conversation. The in-callscreen 140 can identify an alias 141, a name of the talker 142, a timestatistic of talking activity 143, and details 144 associated with thecontact identifier. Notably, the in-call screen 140 can change dependingon which PTT recorded segment is being played. For example, differenttalkers can have different in-call screens which identify the name andthe details for each PTT recorded segment. The in-call screen 140 canalso be presented during the recording of the PTT conversation. Thisallows the first user to visually identify who is talking when recordingor playing back the PTT conversation.

Referring to FIG. 4, a method 300 for data recording and playback forpush-to-talk (PTT) group dispatch call is shown. Briefly, the method 300can be practiced by a mobile device 110 of the wireless communicationsystem 100 using a push-to-cellular (PoC) communication infrastructureas shown in FIG. 1. For example, the mobile device 110 of FIG. 2 canpractice the method 300 for recording and playing back portions of, oran entire, PTT conversation. The method 300 can be practiced with moreor less than the number of steps shown. To describe the method 300,reference will be made to FIGS. 1, 2, 5 and 6 although it is understoodthat the method 300 can be implemented in any other manner using othersuitable components. In addition, the method 300 can contain a greateror a fewer number of steps than those shown in FIG. 4

At step 301, the method 300 can start. The method 300 can start in astate where one or more users are engaged in a group dispatch call. Eachuser can use a different mobile device. The method can start when atleast one user elects to record a push-to-talk conversation. Forexample, referring to FIG. 1, a first user of a first mobile device 110can press a soft-key to begin recording the PTT conversation. The PTTconversation can consist of the first user of the first mobile device110, the second user of the second mobile device 111, and the third userof the third mobile device 112. Notably, more or less than three userscan be in the group call.

At step 302, a push-to-talk (PTT) key-up can be received from a mobiledevice during a group dispatch call. The PTT key-up can acquire the talkchannel of the group dispatch call. For example, referring back to FIG.1, the first mobile device 110 can receive a PTT key-up from the secondmobile device 111 or the third mobile device 112. The PTT key-up isreceived shortly after the second user presses the PTT key 122 toacquire the talk channel.

Referring to FIG. 5, an exemplary PTT conversation 340 is shown. Theexemplary conversation 340 can include three talkers: User 1 (310) onmobile device 110, User 2 (320) on mobile device 111, and User 3 (330)on mobile device 112. A user can press a PTT key 122 of a respectivemobile device to acquire the talk channel. As shown, the PTTconversation 340 can consist of PTT voice segments, though other data,such as video or audio, can also be transmitted on the talk channel.Notably, only one user can speak at a time on the talk channel duringgroup dispatch call. A user can talk after pushing a PTT key. Phrases ofthe PTT conversation are shown in FIG. 5. In the exemplary PTTconversation, a first user 310 asks the other users for a phone number.The second user 320 does not have the number. The third user 330 makes afirst response, then a second response identifying the number.

Referring to FIG. 6, a depiction of the PTT conversation 340 is shown.The depiction shows the PTT voice segments as blocks of data withspecific time intervals. Each PTT voice segment has an associated starttime and end time, corresponding to the PTT key-up and the PTTkey-release, respectively. The time in between PTT voice segments is thehang-time, which is generally silence, and is designated by the initials(HT). However, the hang-time intervals may also include push-to-transmit(PTX) data. At a first time 312, User 1 (310) can push the PTT buttonand say the phrase d1 (311) “Does anyone know the number”. At a secondtime 322, User 2 (320) can push the PTT and say the phrase d2 (321)“Sorry, I don't know”. At a third time 332, User 3 (330) can push thePTT and say the phrase 331 “Wait, let me check”. At a fourth time 334,User 3 (330) can push the PTT and say the phrase d4 (333) “The number is555-1212”. The phrases d1-d4 constitute data and are not restricted toonly voice. For example, the user may send an image or a video duringthe PTT which can also be recorded and marked in memory.

Referring back to FIG. 4, at step 304, a mobile device can be identifiedfrom the PTT key-up. Notably, only one mobile device at a time canacquire the talk channel. The talk channel is acquired when the userpresses the PTT key 122 and successfully acquires a transmit channel forthe group dispatch call. In PoC group dispatch, a mobile device may sendan information packet that identifies the mobile device. The informationpacket may also identify the user that is presently talking on the talkchannel. As an example, the mobile device can send an iCard ordescriptive identifier to inform other mobile devices of the person whois talking. Accordingly, the mobile device 110 can retrieve thedescriptive identifier and determine which mobile device has acquiredthe talk channel. For example, referring to FIG. 2, the modem 120 canidentify when a talk channel is acquired by another mobile device. Theprocessor 126 can decode data packets received by the modem 120 toidentify the mobile device that acquired the talk channel. The processor120 can generate a contact identifier for the mobile device. Uponidentifying the mobile device, a contact identifier can be produced. Inpractice, the mobile device 110 can generate a contact identifier foreach mobile device in the PTT group dispatch call.

Returning back to FIG. 4, at step 306, data can be recorded during thePTT key-up and the PTT key-release to produce a PTT recorded segment.Recall in FIG. 1, the first mobile device 110 can capture the PTTconversation of the group dispatch call in PTT recorded segments. Inparticular, referring back to FIG. 2, the recorder 124 can capture andsave the data on the talk channel. The processor 126 can inform therecorder 124 when to start and stop recording based on the PTT key-upand PTT key-release times. Only data that is communicated on the talkchannel is captured. Silence intervals, such as a hang-time between aPTT key-release and a PTT key-up, are not recorded.

Returning back to FIG. 4, at step 308, the PTT recorded segment can bemarked with the contact identifier. The contact identifier identifiesthe mobile device, or user, of the PTT recorded segment as discussed instep 304. A contact identifier can be a name of a contact, such as theuser of the mobile device, a call session name of the PTT conversation,a time of the PTT recorded segment, or a length of the PTT recordedsegment, but is not limited to these. As previously mentioned, thecontact identifier can be generated from an information packet sent withthe PTT key press, or with a PTX packet. Referring to FIG. 2, theprocessor 126 can mark a PTT recorded segment with the contactidentifier. As illustrated in FIG. 7, the processor 126 can append thecontact identifier to the PTT recorded segment. For instance, thecontact identifier can be stored in memory before the PTT recordedsegment. For example, contact identifier I1 (361) can be stored with PTTrecorded segment d1 (331). In another arrangement, a pointer can beappended with the PTT recorded segment. The pointer can lead to anothermemory space containing the contact information.

Returning back to FIG. 4, at step 310, the PTT recorded segments can besaved with the contact identifier to memory. The memory can be local tothe mobile device or available over a network connection. For example,referring back to FIG. 1, the first mobile device 110 can store markedPTT segments to a local memory on the phone, or to a server on thewireless communication network 100. In such regard, the PTT conversationcan be made available to other participants. Referring to FIG. 2, theprocessor 126 can save the marked PTT recorded segment to memory.Notably, the processor 126 can generate multiple marked PTT recordedsegments for each mobile device engaged in the PTT group dispatch call.Accordingly, the method 300 can return to step 302 to continue recordingthe PTT conversation. The method 300 can end when the user thatinitiated the recording of the PTT conversation ends the recording, orthe group dispatch call. The method can end at step 311.

Referring to FIG. 7, a marked PTT 360 conversation is shown. In onearrangement, the marked PTT conversation can be stored in memory asshown. The marked PTT conversation 360 corresponds to the PTTconversation 340 of FIG. 6. In particular, the marked PTT conversation360 includes contact identifiers appended to each PTT recorded segment.It should be noted, that the contact identifiers do not have to beappended to each PTT recorded segment. In another arrangement, the PTTrecorded segments can be categorized by contact identifier.

Notably, the marked PTT conversation 360 is a result of a mobile deviceperforming the method 300 of FIG. 4 for the PTT conversation 340. Themarked PTT conversation 360 includes PTT recorded segments with contactidentifiers. The marked PTT conversation 360 individually identifiesusers and their associated PTT recorded segments. For example, User 1(310) is associated with PTT recorded segment d1 (311) through contactidentifier I1 (361). User 2 (320) is associated with PTT recordedsegment d2 (321) through contact identifier I2 (362). User 3 (330) isassociated with PTT recorded segment d3 (331) through contact identifierI2 (363), and PTT recorded segment d4 (333) through contact identifierI4 (364). The marked PTT conversation 360 can be stored in local memoryon the mobile device or on a server in the network.

In one arrangement, the mobile device can play the marked PTTconversation back by contact identifier. For example, upon completion ofthe PTT dispatch group call, a first user may desire to retrieve all PTTrecorded segments associated with a second user. The first user, canenter a contact identifier of the second user, and the processor 126 canplay back only the PTT recorded segments associated with the seconduser. In another arrangement, the mobile device can play the PTTconversation back by call session. In this case, each PTT recordedsegment can be played back with a corresponding contact identifier. Acontact identifier for each PTT recorded segment can be visually oraudibly presented. The identifier may be suppressed for PTT recordedsegments having the same user. That is, a contact identifier can beprovided only when the PTT recorded segment corresponds to a differentuser, or mobile device.

Referring to FIG. 8, a method 230 for playback by call identifier isshown. Briefly, the mobile device 110 can practice the method 230 toretrieve PTT recorded segments from the marked PTT conversation 360 bycontact identifier. For instance, a first user may remember a seconduser saying a phrase, but not remember a particular date of the groupdispatch call, or when the user said the phrase in the PTT conversation.In such regard, the user can specify the name of the second user, andthe mobile device can automatically retrieve PTT recorded segments froma marked PTT conversation. This allows the first user to listen to voicerecordings of only the second user. The first user is thus not requiredto listen to the entire PTT conversation during playback. Reference willalso be made to FIG. 7, for describing the method 230.

At step 232, the marked PTT conversation can be sorted by contactidentifier. As an example, with respect to the PTT conversation 340 ofFIG. 5, User 1 (310) may request to play back only PTT recorded segmentsassociated with User 3 (330). Recall, each PTT recorded segment wasmarked with a contact identifier during recording, as shown in FIG. 7.Accordingly, the mobile device can identify PTT recorded segments by thecontact identifier. The processor 126 can identify PTT recorded segment311 from contact identifier 363, and PTT recorded segment 331 fromcontact identifier 364. Referring to FIG. 9, the processor selects onlythe PTT recorded segments associated with User 3 (330). In anotherarrangement, PTT recorded segments from the same user can be groupedtogether for each contact identifier. A single voice recording can becreated for each user. In such regard, a user can access the separatevoice recordings directly, without referring to the marked PTTconversation 360. For example, the mobile device store voice recordingsfor different users separately. Instead of entering a contactidentifier, the user can select the voice recordings by user name.

Returning back to FIG. 8, at step 234 the PTT recorded segments can beplayed back by contact identifier in order of recording. For example,upon identifying the PTT recorded segments for User 3 (330), theprocessor 126 can playback the PTT recorded segments for User 3 (330) inthe time order captured. The processor 126 can also pre-append a contactidentifier to the playback to identify the user. For example, as shownin FIG. 10, the processor 126 can append the audible phrase “User 3said” (350) to the voice recorded data “Wait, let me check” (311) and“The number is 555-1212” (331). The user of the mobile device will hear“User 3 said, Wait, let me check, The number is 555-1212”. In suchregard, the user is able to access only the PTT recordings of a specificuser, by contact identifier. Moreover, only the PTT recorded segmentsassociated with the contact identifier are played back to the user.

Referring to FIG. 11, a method 240 for playback by call session isshown. Briefly, a mobile device can practice the method 240 to replaythe entire PTT conversation with contact identifiers. In playback bycall session, visual or auditory indicators can be presented with eachPTT recorded segment. For example, during playback, the name of a talkerof a PTT recorded segment can be visually presented on a display. Asanother example, the name can be synthesized to voice and pre-appendedto the PTT recorded segment to identify, or introduce, the talker. Thisallows the first user to determine who is talking during playback of themarked PTT conversation. Reference will also be made to FIG. 7, fordescribing the method 240.

At step 242, a call session associated with a marked PTT conversationcan be identified. A call session is a description for a PTTconversation. For example, a user, upon recording a PTT conversation cansave the marked PTT conversation under a filename. The filenameidentifies the call session and can be presented in the display of themobile device. For example, referring back to FIG. 2, the mobile device110 can present a list of call sessions on the display 126. A user canpick from one of the call sessions listed. Accordingly, the processor126 can retrieve the marked PTT conversation associated with the callsession.

Referring to FIG. 12, the marked PTT conversation 360 of FIG. 7, isshown in an appropriate time order. That is, each of the PTT recordedsegments are presented in the same order as they were recorded. Notably,each PTT recorded segment also has an associated contact identifier. Thecontact identifier can identify a name of the talker for the PTTrecorded segment, a length of the PTT recorded segment 333, a start timeof the PTT recorded segment, or any other details associated with thePTT recorded segment.

Returning back to FIG. 11, at step 244, the PTT recorded segments of thecall session can be played back in order of recording. Moreover, thecontact identifier associated with each PTT recorded segment can bepresented for each PTT recorded segment as the call session is playedback. As one example, referring back to FIG. 2, the text to speechengine 129 can synthesize a voice tag from a contact identifier. Thevoice tag may be a user name retrieved from the contact identifier. Thevoice tag can be pre-appended to the PTT recorded segment to identifythe talker. For example, referring to FIG. 13, the first PTT recordedsegment can include a pre-appended voice tag (361) “User 1 said”followed by the PTT recorded segment “Does anyone know the number?”.Similarly, the second PTT recorded segment can include a pre-appendedvoice tag (362) “User 2 said” followed by the PTT recorded segment“Sorry, I don't know”. The third and fourth PTT recorded segment can besimilarly constructed by pre-appending a voice tag. In such regard, eachPTT recorded segment can be preceded by an indicator, or anintroduction, to the talker if the PTT recorded segment. The playback ofthe call session can be “USER 1 said, Does anyone know the number, USER2 said, Sorry I don't know, USER 3 said, Wait, let me check, The numberis 555-1212”. The processor 126 can also insert pauses between PTTrecorded segments to provide more natural sounding speech. Notably, theprocessor 126 can also suppress a contact identifier for a consecutivetalker. For example, the third user is only introduced once, since thelast two PTT recorded segments were both by the third user.

In another arrangement, the contact identifier can be visuallypresented. For example, referring back to FIG. 2, the processor 126 canpresent a name of the talker, from the contact identifier, on thedisplay 128. More specifically, referring to FIG. 4, the name of thetalker 142 can be visually presented on the in-call screen 140 of thedisplay 128 Notably, the in-call screen 140 can present attributes ofthe contact identifier for each PTT recorded segment during playback.Accordingly, a user can visually identify the talker of a PTT recordedsegment during a playback of the marked PTT conversation. The processor126 can also present any other data associated with the contactidentifier captured during the recording of the PTT conversation. Forexample, in a PoC group call, every participant can send differentPush-to-talk (PTX) data, such as an iCard or event, in response topressing of the PTT key 122. The processor 126 can save the PTX data tomemory, and present the data during playback in the in-call screen 140.This also allows the user to retrieve the PTX data during the playback.For example, during the PTT conversation, a user may transmit an imagefor other users to see. Accordingly, the processor 126 can store theimage, which can be made available for retrieval during playback.

Where applicable, the present embodiments of the invention can berealized in hardware, software or a combination of hardware andsoftware. Any kind of computer system or other apparatus adapted forcarrying out the methods described herein are suitable. A typicalcombination of hardware and software can be a mobile communicationsdevice with a computer program that, when being loaded and executed, cancontrol the mobile communications device such that it carries out themethods described herein. Portions of the present method and system mayalso be embedded in a computer program product, which comprises all thefeatures enabling the implementation of the methods described herein andwhich when loaded in a computer system, is able to carry out thesemethods.

While the preferred embodiments of the invention have been illustratedand described, it will be clear that the embodiment of the invention isnot so limited. Numerous modifications, changes, variations,substitutions and equivalents will occur to those skilled in the artwithout departing from the spirit and scope of the present embodimentsof the invention as defined by the appended claims.

1. A method for voice record and playback in push-over-cellular (PoC),the method comprising: recording a PTT conversation in PTT recordedsegments; identifying mobile devices from (PTT) key-ups during the PTTconversation to produce contact identifiers; assigning the contactidentifiers to the PTT recorded segments to produce a marked PTTconversation; and saving the marked PTT conversation to memory, whereina PTT recorded segment is a portion of the PTT conversation capturedbetween a PTT key-up and a PTT key-release.
 2. The method of claim 1,further comprising identifying a user of a mobile device frompush-to-transmit (PTX) data such as an iCard or an event message.
 3. Themethod of claim 1, further comprising: receiving a contact identifier;sorting the marked PTT conversation by the contact identifier; andplaying back PTT recorded segments associated with the contactidentifier in order of recording.
 4. The method of claim 1, furthercomprising: identifying a call session associated with the marked PTTconversation; and playing back the PTT recorded segments in order ofrecording, wherein at least one PTT recorded segment is preceded by acontact identifier.
 5. The method of claim 1, further comprisingvisually presenting a contact identifier on a display during a playbackof a PTT recorded segment.
 6. The method of claim 1, further comprisingaudibly presenting a contact identifier by pre-appending a voice tag toa PTT recorded segment during a playback of a PTT recorded segment. 7.The method of claim 1, wherein a contact identifier is a name of a user,an alias, a mobile device identifier, a talk activity indicator, a callsession name of the PTT conversation, a time of the PTT recordedsegment, or a length of the PTT recorded segment.
 8. The method of claim1, wherein the step of recording a push-to-talk PTT group call furthercomprises: receiving a request to record a PTT conversation; identifyinga PTT key-up from a mobile device in the PTT conversation; identifyingthe mobile device performing the PTT key-up; and capturing dataassociated with the PTT key-up.
 9. The method of claim 1, wherein thedata is voice, video, image, picture, or audio that is shared andcaptured during the PTT conversation.
 10. A method for call sessionrecording and playback in Push-over-Cellular (PoC), comprising:receiving a push-to-talk (PTT) key-up from a first mobile device duringa group dispatch call; identifying the first mobile device from the PTTkey-up to produce a first contact identifier; recording data during thePTT key-up until a PTT key-down is received to produce a PTT recordedsegment; marking the PTT recorded segment with the contact identifier;storing the first PTT recorded segment to memory; and repeating thesteps of receiving, identifying, recording, marking, and storing for aplurality of mobile devices on the group dispatch call for producing amarked PTT conversation having multiple PTT recorded segments.
 11. Themethod of claim 10, further comprising: receiving a request to retrievePTT recorded segments, the request providing a contact identifier; andpresenting the PTT recorded segments for the contact identifier in orderof recording in response to the request.
 12. The method of claim 10,further comprising: identifying a call session associated with themarked PTT conversation; and playing back the PTT recorded segments bythe call session in order of recording, wherein at least one PTTrecorded segment is preceded by a contact identifier.
 13. The method ofclaim 12, wherein the playing back further comprises pre-appending avoice tag on a PTT recorded segment.
 14. The method of claim 12, whereinthe playing back further comprises visually displaying a contactidentifier during a PTT recorded segment.
 15. The method of claim 10,wherein a contact identifier is a name of the contact, a name of the PTTconversation, a time of the PTT recorded segment, a length of the PTTrecorded segment.
 16. A mobile device for call session recording andplayback, comprising: a push-to-talk (PTT) key that acquires a talkchannel and communicates data during a PTT group call; a recorderoperatively coupled to the talk channel that records the PTT group callin PTT recorded segments, wherein a PTT recorded segment is a recordingof data between a time of a PTT key-up and a PTT key-release; and aprocessor operatively coupled to the recorder that assigns contactidentifiers to the PTT recorded segments to produce a marked PTTconversation, wherein a contact identifier identifies a mobile deviceperforming the PTT key-up and a PTT key-release.
 17. The mobile deviceof claim 16, wherein the processor identifies other mobile devices thatacquire the talk channel, and generates a contact identifier for theother mobile devices, wherein the contact identifier includes a name ofa user of the mobile device, a time the talk channel is acquired, and alength of the PTT recorded segment.
 18. The mobile device of claim 16,wherein the processor sorts the marked PTT conversation by contactidentifier, and plays back the PTT recorded segments associated with thecontact identifier in order of recording.
 19. The mobile device of claim16, further comprising: a display operatively coupled to the processorthat visually shows a contact identifier associated with a PTT recordedsegment
 20. The mobile device of claim 16, further comprising: atext-to-speech engine operatively coupled to the processor thatpre-appends a voice tag on a PTT recorded segment.